Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update wrangler #781

Merged
merged 1 commit into from
Dec 23, 2024
Merged

fix(deps): update wrangler #781

merged 1 commit into from
Dec 23, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 7, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@cloudflare/workers-types ^4.20241022.0 -> ^4.20241218.0 age adoption passing confidence
wrangler (source) ^3.85.0 -> ^3.99.0 age adoption passing confidence

Release Notes

cloudflare/workerd (@​cloudflare/workers-types)

v4.20241218.0

Compare Source

v4.20241216.0

Compare Source

v4.20241214.0

Compare Source

v4.20241205.0

Compare Source

v4.20241202.0

Compare Source

v4.20241127.0

Compare Source

v4.20241112.0

Compare Source

cloudflare/workers-sdk (wrangler)

v3.99.0

Compare Source

Minor Changes

  • #​7425 8757579 Thanks @​CarmenPopoviciu! - feat: Make DX improvements in wrangler dev --remote

    Workers + Assets projects have, in certain situations, a relatively degraded wrangler dev --remote developer experience, as opposed to Workers proper projects. This is due to the fact that, for Workers + Assets, we need to make extra API calls to:

    1. check for asset files changes
    2. upload the changed assets, if any

    This commit improves the wrangler dev --remote DX for Workers + Assets, for use cases when the User Worker/assets change while the API calls for previous changes are still in flight. For such use cases, we have put an exit early strategy in place, that drops the event handler execution of the previous changes, in favour of the handler triggered by the new changes.

  • #​7537 086a6b8 Thanks @​WillTaylorDev! - Provide validation around assets.experimental_serve_directly

  • #​7568 2bbcb93 Thanks @​WillTaylorDev! - Warn users when using smart placement with Workers + Assets and serve_directly is set to false

Patch Changes

  • #​7521 48e7e10 Thanks @​emily-shen! - feat: add experimental_patchConfig()

    experimental_patchConfig() can add to a user's config file. It preserves comments if its a wrangler.jsonc. However, it is not suitable for wrangler.toml with comments as we cannot preserve comments on write.

  • Updated dependencies [1488e11, 7216835]:

v3.98.0

Compare Source

Minor Changes

  • #​7476 5124b5d Thanks @​WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets.
    These assets will be served as though the assets directly were mounted to the root.
    For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.

  • #​7380 72935f9 Thanks @​CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

  • #​7573 fb819f9 Thanks @​emily-shen! - feat: add experimental_readRawConfig()

    Adds a Wrangler API to find and read a config file

  • #​7549 42b9429 Thanks @​penalosa! - Expand metrics collection to:

    • Detect Pages & Workers CI
    • Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv

  • #​7583 8def8c9 Thanks @​penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

v3.97.0

Compare Source

Minor Changes

  • #​7522 6403e41 Thanks @​vicb! - feat(wrangler): allow overriding the unenv preset.

    By default wrangler uses the bundled unenv preset.

    Setting WRANGLER_UNENV_RESOLVE_PATHS allow to use another version of the preset.
    Those paths are used when resolving the unenv module identifiers to absolute paths.
    This can be used to test a development version.

  • #​7479 2780849 Thanks @​penalosa! - Accept a JSON file of the format { name: string }[] in wrangler kv bulk delete, as well as the current string[] format.

Patch Changes

v3.96.0

Compare Source

Minor Changes
Patch Changes

  • #​7542 f13c897 Thanks @​CarmenPopoviciu! - Always print deployment and placement ID in Cloudchamber commands

    Currently, Cloudchamber commands only print the full deployment ID when the deployment has an IPv4 address. This commit ensures the deployment ID and the placement ID are always printed to stdout. It also moves the printing of the IPv4 address (if one exists) to the same place as the IPv6 address so that they are printed together.

  • #​6754 0356d0a Thanks @​bluwy! - refactor: move @cloudflare/workers-shared as dev dependency

  • #​7478 2e90efc Thanks @​petebacondarwin! - fix: ensure that non-inherited fields are not removed when using an inferred named environment

    It is an error for the the user to provide an environment name that doesn't match any of the named environments in the Wrangler configuration.
    But if there are no named environments defined at all in the Wrangler configuration, we special case the top-level environment as though it was a named environment.
    Previously, when this happens, we would remove all the nonInheritable fields from the configuration (essentially all the bindings) leaving an incorrect configuration.
    Now we correctly generate a flattened named environment that has the nonInheritable fields, plus correctly applies any transformFn on inheritable fields.

  • #​7524 11f95f7 Thanks @​gpanders! - Include response body in Cloudchamber API errors

  • #​7427 3bc0f28 Thanks @​edmundhung! - The x-provision experimental flag now identifies draft and inherit bindings by looking up the current binding settings.

    Draft bindings can then be provisioned (connected to new or existing KV, D1, or R2 resources) during wrangler deploy.

  • Updated dependencies []:

v3.95.0

Compare Source

Minor Changes

v3.94.0

Compare Source

Minor Changes
  • #​7229 669d7ad Thanks @​gabivlj! - Introduce a new cloudchamber command wrangler cloudchamber apply, which will be used by customers to deploy container-apps
Patch Changes

v3.93.0

Compare Source

Minor Changes

  • #​7291 f5b9cd5 Thanks @​edmundhung! - Add anonymous telemetry to Wrangler commands

    For new users, Cloudflare will collect anonymous usage telemetry to guide and improve Wrangler's development. If you have already opted out of Wrangler's existing telemetry, this setting will still be respected.

    See our data policy for more details on what we collect and how to opt out if you wish.

  • #​7448 20a0f17 Thanks @​GregBrimble! - feat: Allow Workers for Platforms scripts (scripts deployed with --dispatch-namespace) to bring along assets

  • #​7445 f4ae6ee Thanks @​WillTaylorDev! - Support for assets.experimental_serve_directly with wrangler dev

Patch Changes

v3.92.0

Compare Source

Minor Changes

  • #​7251 80a83bb Thanks @​penalosa! - Improve Wrangler's multiworker support to allow running multiple workers at once with one command. To try it out, pass multiple -c flags to Wrangler: i.e. wrangler dev -c wrangler.toml -c ../other-worker/wrangler.toml. The first config will be treated as the primary worker and will be exposed over HTTP as usual (localhost:8787) while the rest will be treated as secondary and will only be accessible via a service binding from the primary worker. Notably, these workers all run in the same runtime instance, which should improve reliability of multiworker dev and fix some bugs (RPC to cross worker Durable Objects, for instance).

  • #​7130 11338d0 Thanks @​nickbabcock! - Update import resolution for files and package exports

    In an npm workspace environment, wrangler will now be able to successfully resolve package exports.

    Previously, wrangler would only be able to resolve modules in a relative node_modules directory and not the workspace root node_modules directory.

  • #​7355 5928e8c Thanks @​emily-shen! - feat: add experimental_serve_directly option to Workers with Assets

    Users can now specify whether their assets are served directly against HTTP requests or whether these requests always go to the Worker, which can then respond with asset retrieved by its assets binding.

Patch Changes

v3.91.0

Compare Source

Minor Changes

  • #​7230 6fe9533 Thanks @​penalosa! - Turn on wrangler.json(c) support by default

    Wrangler now supports both JSON (wrangler.json) and TOML (wrangler.toml) for it's configuration file. The format of Wrangler's configuration file is exactly the same across both languages, except that the syntax is JSON rather than TOML. e.g.

    name = "worker-ts"
main = "src/index.ts"
compatibility_date = "2023-05-04"

    would be interpreted the same as the equivalent JSON

    {
  "name": "worker-ts",
  "main": "src/index.ts",
  "compatibility_date": "2023-05-04"
}

  • #​7330 219109a Thanks @​jonesphillip! - Added Oceania (oc) location hint as acceptable choice when creating an R2 bucket.

  • #​7227 02a0e1e Thanks @​taylorlee! - Add preview_urls toggle to wrangler.toml

    The current Preview URLs (beta) feature routes to version preview urls based on the status of the workers_dev config value. Beta users have requested the ability to enable deployment urls and preview urls separately on workers.dev, and the new previews_enabled field of the enable-subdomain API will allow that. This change separates the workers_dev and preview_urls behavior during wrangler triggers deploy and wrangler versions upload. preview_urls defaults to true, and does not implicitly depend on routes the way workers_dev does.

  • #​7308 1b1d01a Thanks @​gpanders! - Add a default image for cloudchamber create and modify commands

  • #​7232 7da76de Thanks @​toddmantell! - feat: implement queues info command

    This command allows users to get information on individual queues.

    To run this command use the queues info command with the name of a queue in the user's account.

    wrangler queues info my-queue-name

Patch Changes

v3.90.0

Compare Source

Minor Changes
Patch Changes

v3.89.0

Compare Source

Minor Changes
Patch Changes

  • #​7314 a30c805 Thanks @​Ankcorn! - Fix observability.logs.enabled validation

  • #​7285 fa21312 Thanks @​penalosa! - Rename directory to projectRoot and ensure it's relative to the wrangler.toml. This fixes a regression which meant that .wrangler temporary folders were inadvertently generated relative to process.cwd() rather than the location of the wrangler.toml file. It also renames directory to projectRoot, which affects the `unstable_startWorker() interface.

  • Updated dependencies [563439b]:

v3.88.0

Compare Source

Minor Changes

  • #​7173 b6cbfbd Thanks @​Ankcorn! - Adds [observability.logs] settings to wrangler. This setting lets developers control the settings for logs as an independent dataset enabling more dataset types in the future. The most specific setting will win if any of the datasets are not enabled.

    It also adds the following setting to the logs config

    • invocation_logs - set to false to disable invocation logs. Defaults to true.
    [observability.logs]
enabled = true
invocation_logs = false

  • #​7207 edec415 Thanks @​jonesphillip! - Added r2 bucket lifecycle command to Wrangler including list, add, remove, set

Patch Changes

v3.87.0

Compare Source

Minor Changes
Patch Changes

v3.86.1

Compare Source

Patch Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the renovate label Nov 7, 2024
@renovate renovate bot changed the title fix(deps): update dependency @cloudflare/workers-types to ^4.20241106.0 fix(deps): update wrangler Nov 8, 2024
@renovate renovate bot force-pushed the renovate/wrangler branch 5 times, most recently from 8145d5f to 86518d6 Compare November 14, 2024 19:28
@renovate renovate bot force-pushed the renovate/wrangler branch 4 times, most recently from ba38e0d to f739d67 Compare November 26, 2024 15:06
@renovate renovate bot force-pushed the renovate/wrangler branch 3 times, most recently from a7e6133 to c5aec81 Compare December 3, 2024 01:22
@renovate renovate bot force-pushed the renovate/wrangler branch 5 times, most recently from c663c37 to 90c7980 Compare December 10, 2024 19:23
@renovate renovate bot force-pushed the renovate/wrangler branch 7 times, most recently from 7ad6db0 to 19bd667 Compare December 19, 2024 09:46
@renovate renovate bot force-pushed the renovate/wrangler branch from 19bd667 to 1a6422f Compare December 19, 2024 19:32
@yjl9903 yjl9903 merged commit fd9426c into main Dec 23, 2024
1 check passed
@renovate renovate bot deleted the renovate/wrangler branch December 23, 2024 08:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
renovate
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@yjl9903